This pr updates java-eks-otlp-test 3p actions from VID to CSHA after we've verified functionality.

Dotnet: https://github.com/aws-observability/aws-otel-dotnet-instrumentation/actions/runs/17954504745
JS: https://github.com/aws-observability/aws-otel-js-instrumentation/actions/runs/17953179640
Java: https://github.com/aws-observability/aws-otel-java-instrumentation/actions/runs/17954706776
Python: https://github.com/aws-observability/aws-otel-python-instrumentation/actions/runs/17953142892

To do so, create a test.yml file with name: Test and workflow description to test your changes, then remove the file for your PR. Link your test run in your PR description. This process is a short term solution while we work on creating a staging environment for testing.

NOTE: TESTS RUNNING ON A SINGLE EKS CLUSTER CANNOT BE RUN IN PARALLEL. See the needs keyword to run tests in succession.

• Run Java EKS on e2e-playground in us-east-1 and eu-central-2
• Run Python EKS on e2e-playground in us-east-1 and eu-central-2
• Run metric limiter on EKS cluster e2e-playground in us-east-1 and eu-central-2
• Run EC2 tests in all regions
• Run K8s on a separate K8s cluster (check IAD test account for master node endpoints; these will change as we create and destroy clusters for OS patching)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.